State-sensitive navigation aid

ABSTRACT

Navigation logic and related methods are described for assisting a user in using a remote control (RC) device. The navigation logic determines a current state of a user&#39;s interaction with an application, and then determines the keys of the RC device that are relevant to the determined state. The navigation logic then displays a representation of the relevant keys on a user interface presentation of a presentation device. The representation resembles a physical layout of associated physical keys on the RC device. To assist the user in focusing on the relevant keys, the representation de-emphasizes other input mechanisms of the RC device that do not have a bearing on the user&#39;s current interaction with the application. One exemplary way of de-emphasizing these other keys is to entirely omit these keys from the representation.

BACKGROUND

Advances in media processing and presentation equipment (“mediaequipment”) have greatly expanded the versatility of such mediaequipment. For example, conventional television has evolved intofunctionality that can also potentially be used to display and interactwith electronic program guide (EPG) data, browse and selectvideo-on-demand (VOD) assets (e.g., movies), record and play back mediaprograms, play games, interact with a wide area network (such as theInternet), shop and perform other commerce-related tasks, communicatewith other users, and so forth.

However, expanding the versatility of media equipment also introducesnew challenges. For instance, the increased versatility may equate to anincrease in complexity of the media equipment. Such an increase incomplexity may make it more difficult for the users to learn how to usethe media equipment. From the standpoint of the user, this may causefrustration, as users typically engage in media equipment to fill theirleisure time, not to develop quasi-computer-related skills. From thestandpoint of the provider of the media equipment, the added complexityof the media equipment may result in users failing to fully engage themedia equipment, which may equate to loss of revenue for the provider.

One aspect of media equipment that has become increasingly complex overthe years is the remote control (RC) device. The RC device is used by auser to interact with applications that run on the media equipment. Morespecifically, the RC device is conventionally used to change channels,adjust the volume, control the recording and playback of media programs,navigate among miscellaneous user interface options, and so forth.However, as the media equipment has become more versatile by adoptingadditional features, RC devices have become more complex in lockstep. Itis not uncommon for a user to rely on a very complex RC device havingmany dozens of input buttons. Furthermore, it is not uncommon for a userto rely on multiple RC devices, with different RC devices controllingdifferent media processing devices. As a result of this complexity, evenexperienced users must sometimes spend a few moments hunting for an RCbutton which will invoke a desired function in the context of aparticular media equipment application. This problem is, of course,exacerbated in the case of novice users, who may ultimately have to aska more experienced user to point out the location of the sought-afterbutton. It may also become difficult for any user to fully master theinterface between the RC device and the media equipment, becausedifferent applications of the media equipment may redefine (e.g., remap)the functionality assigned to the buttons on the RC device, requiringthe user to relearn the purpose served by the buttons in the context ofnew applications.

As appreciated by the present inventors, there is therefore an exemplaryneed in the art to provide functionality for assisting a user in usingan RC device, and thereby assisting the user in interacting with anapplication provided by the media equipment.

SUMMARY

According to one exemplary implementation, navigation logic and relatedmethods are described for assisting a user in using a remote control(RC) device. The navigation logic determines a current state of a user'sinteraction with an application, and then determines the keys of theactual RC device that are relevant to the determined state. Thenavigation logic then displays a representation of the relevant keys ona user interface presentation of a presentation device. Therepresentation resembles a physical layout of associated physical keyson the RC device. To assist the user in focusing on the relevant keys,the representation de-emphasizes other input mechanisms of the RC devicethat do not have a bearing on the user's current interaction with theapplication. One exemplary way of de-emphasizing these other keys is toentirely omit these keys in the representation.

Through the use of the above-described provisions, the navigation logicguides the user in the use of the RC device. Namely, at any juncture ina user's interaction with an application, the navigation logiceffectively highlights those keys which are relevant to a task at hand.These provisions have the effect of better integrating the user with theapplication being controlled via the RC device, that is, by more closelytying the user's actions with respect to the RC device with theapplication being controlled.

Numerous benefits ensue from the use of the navigation logic. Forexample, the navigation logic potentially reduces the user's confusionand frustration in interacting with an application. The navigation logicalso potentially makes it more likely that the user will actively engagewith the application, which may result in improved revenue for theentity which provides the application.

Additional implementations and features will be described in thefollowing.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an exemplary system for implementing navigation logic thatguides a user in the use of a remote control (RC) device in the contextof an application controlled by the RC device.

FIG. 2 shows an exemplary processing device used in the system of FIG. 1for implementing the navigation logic.

FIG. 3 shows an exemplary one of many possible kinds of RC devices thatcan be used to interact with the system of FIG. 1.

FIGS. 4-8 show different exemplary user interface presentations that canbe presented by the navigation logic.

FIG. 9 shows an exemplary alternative or supplemental technique forguiding a user in the use of the RC device, involving the presentationof prompting cues at the RC device itself.

FIG. 10 shows an exemplary procedure for guiding a user in the use ofthe RC device in the context of an application controlled by the RCdevice.

The same numbers are used throughout the disclosure and figures toreference like components and features. Series 100 numbers refer tofeatures originally found in FIG. 1, series 200 numbers refer tofeatures originally found in FIG. 2, series 300 numbers refer tofeatures originally found in FIG. 3, and so on.

DETAILED DESCRIPTION

To facilitate discussion, the navigation logic will be described in theexemplary context of functionality which presents media information tousers. The term “media information,” as used herein, refers to any datarepresented in electronic form that can be consumed by a user. The mediainformation can include any information that conveys audio and/or videoinformation, such as audio resources (e.g., music, spoken word subjectmatter, etc.), still picture resources (e.g., digital photographs,etc.), moving picture resources (e.g., audio-visual television mediaprograms, movies, etc.), and so on. The term “media program” representsany unit of media information that can be consumed by a client device.For example, a media program may represent a television media program, amovie, a piece of music, and so forth.

However, the navigation logic can be applied to other applications whichdo not involve the presentation of and interaction with mediainformation. More generally stated, the navigation logic finds exemplaryuse in any environment in which a user interacts with any kind ofapplication using any kind of input device. For example, the navigationlogic can be used to assist a game player in using a control device bydisplaying an on-screen representation of the input mechanisms of thecontrol device which are relevant to a current phase or level of thegame being played. As another example, the navigation logic can be usedto assist a computer user in using an input device (such as a mousedevice or keyboard) by displaying a representation of the inputmechanisms which are relevant to an application task at hand.

This disclosure includes the following sections. Section A describes anexemplary architecture for implementing the navigation logic describedherein. Section B describes exemplary user interface presentations (or“pages”) produced by the navigation logic, and related features. SectionC describes exemplary procedures which explain the behavior of thenavigation logic.

A. Exemplary Architecture for Implementing Navigation Logic

Generally, any of the functions described with reference to the figurescan be implemented using software, firmware (e.g., fixed logiccircuitry), manual processing, or a combination of theseimplementations. The term “logic, “module” or “functionality” as usedherein generally represents software, firmware, or a combination ofsoftware and firmware. For instance, in the case of a softwareimplementation, the term “logic,” “module,” or “functionality”represents media program code (and/or declarative-type instructions)that performs specified tasks when executed on a processing device ordevices (e.g., CPU or CPUs). The media program code can be stored in oneor more computer readable memory devices. More generally, theillustrated separation of logic, modules and functionality into distinctunits may reflect an actual physical grouping and allocation of suchsoftware and/or hardware, or can correspond to a conceptual allocationof different tasks performed by a single software media program and/orhardware unit. The illustrated logic, modules and functionality can belocated at a single site (e.g., as implemented by a processing device),or can be distributed over plural locations.

A.1. Exemplary System

FIG. 1 shows an exemplary system 100 for implementing the navigationlogic described herein. Broadly, the system 100 includes an end-useenvironment 102 that receives media information from one or more mediasources 104 via a coupling mechanism 106. The end-use environment 102may correspond to a home (or room in home) in which a user consumesmedia programs delivered by the media sources 104. Only one end-useenvironment 102 is shown to simplify the drawing; however, the readerwill appreciate that the system 100 can include a great number ofend-use environments, e.g., corresponding to different homes ordifferent rooms within a single home. The explanation for the exemplaryend-use environment 102 therefore applies to all other end-useenvironments (not shown).

Exemplary end-use environment 102 includes a processing device 108coupled to a presentation device 110. The user interacts with theprocessing device 108 via a remote control (RC) device 112. Theprocessing device 108 provides functionality for processing andpresenting media information. In one case, the processing device 108 cancorrespond to a separate unit which couples to the presentation device110 via one or more communication channels. For example, the processingdevice 108 may correspond to a set-top box which is coupled to thepresentation device 110 via appropriate hardwired or wirelesscommunication channels. Or the processing device 108 may represent adigital video disk player (DVD), a digital video recorder (DVR), adigital video disc rewritable (DVD-RW), etc., or any combination ofthese kinds of devices. In another case, the processing device 108 maycorrespond to functionality which is integrated into the presentationdevice 110 itself.

The presentation device 110 can correspond to any unit for presentingmedia information. In the most common case evoked in this explanation,the presentation device 110 corresponds to a television unit. But thepresentation device 110 can also correspond to a unit which presentsonly audio information (e.g., a stereo system), a computer monitordisplay, and so forth.

The RC device 112 corresponds to any unit which allows the user tointeract with the processing device 108. In the most common case evokedin this explanation, the RC device 112 corresponds to a handheld devicethat includes multiple keys that allow the user to control the selectionand playback of media programs, as well as other tasks. Such a handhelddevice typically communicates with the processing device 108 via one ormore wireless channels, such as via infrared signals. However, the RCdevice 112 can alternatively comprise a device which is coupled to theprocessing device 108 via a hardwired link, or a device which isactually integrated into the processing device 108 or the presentationdevice 110 (e.g., as an input panel of the processing device 108 or thepresentation device 110, in which case the qualifier “remote” does notimply that the remote control device is spatially separated from theunit it controls, but merely is a distinct unit which interacts with theunit it controls).

By way of overview, the processing device 108 can present one or moreapplications, and the user can interact with the applications via the RCdevice 112. As used herein, the term “application” broadly representsany functionality that can be implemented by the processing device 108which allows the user to perform one or more tasks. A media-relatedapplication can provide functionality which allows the user to performtasks generally associated with the presentation of media programs,e.g., by interacting with EPG data, selecting VOD assets, controllingthe playback of recorded programs, and so forth. A game-relatedapplication can provide functionality which allows the user to selectand play a game. A commerce-related application can providefunctionality which allows the user to browse through and select goodsand/or services for purchase, and so on. In one case, the processingdevice 108 implements all of the logic necessary to provide anapplication. In another case, a remote entity (such as a head-end serverentity) implements all of the logic necessary to provide an application,in which case the processing device 108 simply acts as a “conduit” whichallows the user to receive and interact with the application. In stillanother case, both the processing device 108 and the remote entity canimplement an application in distributed fashion, splitting thefunctionality between local and remote sites.

The system 100 includes navigation logic (not shown in FIG. 1) whichpresents a user interface presentation 114. The user interfacepresentation 114 presents graphical (and/or textual) informationpertaining to the application. For example, the user interfacepresentation 114 can present electronic program guide (EPG) data. Or theuser interface presentation 114 can present graphical information whichallows the user to browse through and select assets (such as VOD movies,or merchandise in a commerce-related application). Or the user interfacepresentation 114 can present graphical information which allows the userto access information over a wide area network, such as the Internet.This is merely a small sample of many possible uses for the userinterface presentation 114. In one implementation, the processing device108 implements the navigation logic. In another case, a remote entity(such as a head-end entity) implements the navigation logic. In stillanother case, both the processing device 108 and the remote entity canimplement the navigation logic in distributed fashion. To simplify thediscussion, this explanation will assume that the first-mentionedscenario applies—namely, that the processing mechanism 108 locallyimplements the navigation logic.

As will be described in later sections, the navigation logic includesfunctionality which assists the user in interacting with an applicationvia the RC device 112. It performs this task by: determining a currentstate of a user's interaction with the application; determining one ormore keys (or other input mechanisms) of the RC device that are relevantto the determined state; and displaying a representation of the relevantkeys on the user interface presentation 114 of a presentation device110. The representation that is displayed resembles a physical layout ofthe relevant keys on the RC device itself. Further, the displayedrepresentation de-emphasizes other input mechanisms of the RC devicethat do not have a bearing on the user's current interaction with theapplication. One exemplary way to de-emphasize these keys is to entirelyomit these other keys from the representation. Another way is to displaythe relevant keys in a different manner than the de-emphasized keys.

To round out the discussion of FIG. 1, the media source 104 can includeone or more kinds of sources. For instance, the media sources 104 cancomprise a cable source 116 that transmits media programs via hardwiredlines (e.g., coaxial cables) to the end-use environment 102.Alternatively, or in addition, the media sources 104 can comprise abroadcast source 118 that transmits media programs via conventionalwireless transmission from a terrestrial antenna to the end-useenvironment 102 (or from a satellite source to the end-use environment102). Alternatively, or in addition, the media sources 104 can comprisevarious network sources 120 that transmit media programs to the end-useenvironment 102. Alternatively, or in additional, the media sources 104can comprise a local source 122 which provides media programs fromwithin the end-use environment 102 for consumption by the end-useenvironment 102; for example, a local source 122 may correspond to a DVDplayer, a video jukebox, etc. disposed within the end-use environment102 itself. Still further possible sources can be used to provide mediacontent programs, as indicated by the generically labeled “other source”module 124 in FIG. 1.

In general, any of the media sources (116-124) can include any kind ofinfrastructure, such as various equipment for storing media contentprograms, various equipment for processing media content programs,various equipment for transmitting the media content programs, and soon. For example, a network source may include one or more servercomputers for processing and disseminating media programs to the end-useenvironment 102.

In one implementation, the media sources 104 can be configured toprovide a one-way information conduit from the media sources 104 to theend-use environment 102. In another implementation, the media sources104 can be configured to provide a two-way information conduit that alsoaccommodates information transfer from the end-use environment 102 tothe media sources 104; in this case, such transfer can be accomplishedthrough the same coupling mechanism used to transfer information fromthe media sources 104 to the end-use environment 102, or via asupplemental coupling mechanism.

The coupling mechanism 106 can represent any kind of informationconduit, or any combination of information conduits. In one case, thiscoupling mechanism 106 can represent a conventional cable couplingmechanism, local broadcast coupling mechanism, a satellite couplingmechanism, a digital network coupling mechanism, or other kind ofcoupling mechanism or combination thereof. In the case of a digitalnetwork coupling mechanism, the network can be implemented using theInternet, an intranet, a LAN network, and so forth, or some combinationthereof. The coupling mechanism 106 can generally include anycombination of hardwired links and wireless links, antennae,transmitters, routers, repeaters, gateways, etc. In the case where alocal source 122 is used, the coupling mechanism 106 may represent alocal network or point-to-point coupling arrangement implemented withina home.

A.2. Exemplary Processing Mechanism

FIG. 2 shows exemplary contents of the processing device 108. Theprocessing device 108 includes a number of modules. Each of thesemodules can be implemented in software, hardware, or a combination ofsoftware and hardware. To achieve a software implementation, theprocessing device 108 can provide volatile and/or non-volatile memory(not shown) for storing machine readable code and one or more processors(e.g., CPUs) (not shown) for implementing this code. Alternatively,hardware implementations can rely, in whole or in part, onapplication-specific logic circuitry for implementing the prescribedfunctions to be described below.

To begin with, the processing device 108 includes a media sourceinterface module 202 for receiving media programs from the media sources104. The media interface module 202 broadly refers to any functionality(software and/or hardware) for receiving media content programsdepending on the techniques used to transfer the media content programs.For conventional broadcast sources, the media source interface module202 can include one or more physical tuners and reception components fortuning the processing device 108 to channels used by the media sources104 to transmit media programs to the end-use environment 102, fordemodulating the received media programs, and so forth. For networksources, the media source interface module 202 can include various kindsof virtual tuners for “tuning” to and receiving media programs from thenetwork source 120 in unicast and/or multicast fashion, for decoding andprocessing the media programs, and so forth. In the case where two-waycommunication is permitted, the media source interface module 202 canalso include functionality configured to transmit information to themedia sources 104 (or to some other entity). The above-describedexamples are merely representative of a wide range of interfacefunctionality that can be implemented by the media source interfacemodule 202.

The processing device 108 can also include an input interface module 204configured to interact with an input device, such as the RC device 112,a keyboard, a trackball, a joystick, a touch sensitive screen, and soon. In the illustrated implementation in which the processing device 108interacts with the RC device 112, the input interface module 204 caninclude functionality configured to convert infrared signals receivedfrom the RC device 112 into digital signals that can be processed by theprocessing device 108. The input interface module 204 can alsooptionally include a mechanism for transmitting information from theprocessing device 108 to the RC device 112.

The processing device 108 also includes a presentation device interfacemodule 206 for interfacing with the presentation device 110. Forinstance, the presentation device interface module 206 can includefunctionality for formatting video and audio signals for presentation atthe presentation device 110 (which, in this case, is a conventionaltelevision unit). In audio applications, the presentation deviceinterface module 206 can appropriately format audio signals for outputto one or audio output devices (not shown).

The core of the processing functionality provided by the processingdevice 108 is implemented by the processing logic 208. The processinglogic 208 can be implemented by hardwired logic circuitry, by one ormore processing devices (CPUs) running machine readable code, or by acombination of hardware and software. To facilitate discussion, FIG. 2depicts the processing logic 208 as including a plurality of logicmodules, which may correspond to discrete logic circuitry units orsections of computer code that implement different functions. One ofthese modules is operating system logic 210. This module handles variousbackground tasks associated with the operation of the processing device108, such as the transfer of information between different components ofthe processing device 108.

Navigation logic 212 provides the functionality which allows the user tointeract with one or more applications. Stated in another way, thenavigation logic 212 allows the user to navigate within theapplications, e.g., by browsing through options, selecting desiredoptions, and so forth. Among the functions implemented by the navigationlogic is the user interface guidance-related function which is the focusof this disclosure. To implement this function, the navigation logic 202includes: logic configured to determine a current state of the user'sinteraction with an application; logic configured to determine one ormore RC device keys (or other input mechanisms) that are relevant to thedetermined state; and logic configured to display a representation ofthe one or more relevant keys on the user interface presentation 114 ofthe presentation device 110.

As mentioned above, the representation resembles a physical layout ofthe relevant keys on the RC device 112 itself. Further, therepresentation de-emphasizes other input mechanisms of the RC device 112that do not have a bearing on the user's 18 current interaction with theapplication. More specifically, in a particular state, one or more keysmay not be relevant because they do not, or can not, perform any usefulfunction. For example, if an application state corresponds to a scenarioin which the user is at the start of a list that can be browsed through,a left arrow button on the RC device 112 does not serve any function,because the user cannot advance to the left of the first in the list.Similarly, if the user is simply advancing through channels, then the OKor Enter button common included in RC devices does not serve anyfunction, as there is nothing about the simple presentation of a channelthat can be invoked by pressing the OK or Enter button. Accordingly, inthe situations, the navigation logic 212 can de-emphasize these buttons.The next section provides examples of user interface presentations 114which illustrate the behavior of the navigation logic 212.

The navigation logic 212 can implement the above functions in variousways. One exemplary way that the navigation logic 212 can implementedthese function is by providing a series of rules. The rules can beexpressed in if-then type format to map possible states that anapplication may enter to the consequent emphasis and de-emphasis ofappropriate keys. Namely, one rule might read: IF the user is working inmode X and is at the start of a list, THEN de-emphasize the left arrowkey. Another exemplary way that the navigation logic 212 can implementthese functions is by storing a lookup table for each application. Thetable can identify a plurality of different states that a user may enterinto when interacting with an application. The table can also identifythe relevant keys associated with those states.

In use, the navigation logic 212 can first determine a state associatedwith the user's current interaction with an application. The navigationlogic 212 can assess the current state in different ways, such as bymaking note of the particular component of a collection of userinterface pages with which the user is currently interacting, or bymaking note of a particular program code module that the user iscurrently invoking. The navigation logic 212 can apply a particular ruleset or lookup table to map the assessed current state into those RC keyswhich are considered relevant to the current state. In a more compleximplementation, the navigation logic 212 can analyze a series of theuser's recent input actions to better determine the operation that theuser is currently attempting to perform. Still other implementations ofthe navigation logic 212 are possible, including artificial intelligencetools which surmise the current state of the user's interaction with anapplication (and the keys relevant to this interaction) using expertsystem technology.

The navigation logic 212 can present the representation of the relevantkeys in different ways. In one technique, the navigation logic 212 canpresent the representation in the form of a picture-in-picture (PIP).The PIP overlays other visual material presented on the presentationdevice 110 (such as the presentation of the media program beingconsumed). In the case in which the representation of the relevant keysis animated, the navigation logic 212 can present a substream of datafor presentation of the presentation device 110 in PIP form.

As noted above, the illustration of the navigation logic 212 as beingentirely implemented by the processing device 108 is merelyillustrative. In another case, the navigation logic 212 can beimplemented entirely by a remote entity (such as a remote head-endserver). In still another case, the navigation logic 212 can beimplemented by a distributed combination of the processing device 108and a remote entity.

The processing logic 208 can also handle a variety of other functionsnot directly relevant to the navigation behavior featured in thisdescription. FIG. 2 generically labels such other functionality as“other logic” 214.

The processing device 108 can also include one or more storage modules216. These storage modules 216 can include various types of volatile andnon-volatile memory. Exemplary storage modules can be dedicated tostoring program code and/or user data. The storage modules 216 can alsoprovide various floppy disk drives, hard disk drives, optical diskdrives, etc. for storing any kind of information.

Finally, the processing device 108 can include one or more internalcoupling mechanisms 218 for coupling its various modules together. Thesecoupling mechanisms 218 can represent various buses, variouspoint-to-point coupling connections, and so on.

FIG. 2 also shows a simplified depiction of the RC device 112 used tointeract with the processing device 108. The RC device 112 can include acollection of keys 220 that allow the user to enter information. The RCdevice 112 also includes control logic 222 for implementing the RCdevice 112's functionality. That is, the general task assigned to thiscontrol logic 222 is to translate the user key actuations into signalsthat can be transmitted to the input interface module 204 of theprocessing device 108 via wireless (e.g., infrared) transmission or someother channel. This control logic 222 can comprise hardwired circuitryor a processing device that implements machine readable code, or somecombination of hardware and software. The RC device 112 also includes aninterface module 224 for actually performing the wireless transmissionof signals to the processing device 108. The interface module 224 canoptionally receive signals transmitted from the processing device 108.

A.3. Remote Control

FIG. 3 provides a more detailed illustration of the exemplary RC device112 shown in FIG. 2. The selection, shape, style, labeling, andplacement of the keys shown in FIG. 3 is merely illustrative of one ofmany possible RC device designs.

One series of keys 302 (stop, rewind, play, forward, previous, pause,next, etc.) are used to control the presentation of a program in aconventional manner (providing that the presentation of the program canbe controlled in this manner). These keys are referred to as “programcontrol keys” herein. Another series of keys 304 provide a mechanism fornavigating through the user interface presentations (114) of anyapplication. Namely, this series of keys 304 includes left, right, up,and down keys that allow a user to navigate in specific respective“directions” within the user interface presentations 114. An OK keydisposed in the center of these navigation keys allows a user to selector activate a particular item that is currently highlighted (or moregenerally, currently has focus) in the user interface presentation 114.This series of keys 304 is referred to herein as the “applicationnavigation keys.” The other keys shown in FIG. 3 are not pertinent tothe examples set forth in this disclosure.

Again, the keys shown in FIG. 3 are entirely exemplary. For example,additional keys can be added. Alternatively, a subset of the keys shownin FIG. 3 can be omitted. Alternatively, the positional arrangement andstyle of the keys shown in FIG. 3 can be varied in any way.

As will be set forth in the next section, the navigation logic 212displays a graphical representation of the keys shown in the RC device112. In the case most often evoked in this disclosure, the navigationlogic 212 provides an on-screen representation of the applicationnavigation keys 304 (i.e., the directional arrow keys and the OK key).In another possible case, the navigation logic 212 can also provide anon-screen duplication of relevant members of the play control keys 302.More generally, the navigation logic 212 can be used to provide anon-screen display of any combination of keys shown in FIG. 3 (includingall of the keys), or any combination of the keys of any other kind of RCdevice.

As will be discussed, the navigation logic 212 also provides varioussupplemental ways of emphasizing the keys of the RC device 112 that areparticularly pertinent to the user's current interaction with anapplication, such as by adding animation or audio content to thedisplayed relevant keys.

B. Exemplary User Interface Presentations and Related Features

This section, with reference to FIGS. 4-9, sets forth several examplesof user interface presentations 114 (and other features) that can beused to guide the user in the use of the RC device 112. The navigationlogic 212 generates these user interface presentations 114 in the mannerdescribed above.

Beginning with FIG. 4, this figure shows a user interface presentation400 that includes two sections. A first section 402 presents a mediaprogram for consumption by the user, which, in this case, corresponds toa television program (“City Hall”) that airs on a specified channel. Asecond section 404 presents a bar that can provide textual and/orgraphical information relevant to an application with which the user mayinteract.

The second section 404 includes a graphical representation 406 of theapplication navigation keys 304 of the RC device 112 shown in FIG. 3.The representation 406 preferably shows the application navigation keys304 in a manner which corresponds to the physical layout of theapplication navigation keys 304 on the RC device 112 itself. Moreover,the representation 406 highlights members of the application navigationkeys 304 which are directly pertinent to the current state of the user'sinteraction with the application. In this particular case, the up arrow,down arrow, and right arrow (collectively identified in FIG. 4 as the“relevant keys” 408) of the application navigation keys 304 have beendeemed relevant, while the left arrow and the OK button (collectivelyidentified in FIG. 4 as the “non-relevant keys” 410) are not deemed tobe pertinent. Thus, the navigation logic 212 has highlighted (oremphasized) the relevant keys 408, but not the non-relevant keys 410.This situation may correspond to the exemplary case in which the user isat the start of a list of programs, so the left arrow key serves nopurpose, and is consequently de-emphasized. Further, in this state, theOK key may not serve a purpose (because there is nothing to select oractivate), and is therefore also de-emphasized.

The navigation logic 212 can use different techniques to emphasize andde-emphasize keys in the representation 406. One technique is toentirely eliminate the display of the non-relevant keys 410 so that theuser does not even see these keys. Another technique is to display therelevant keys 408 in a different manner than the non-relevant keys 410.For example, the non-relevant keys 410 can be displayed as less brightor more transparent than the relevant keys 408. Or the non-relevant keys410 can be displayed in a different color than the relevant keys 408.Still other graphical techniques are possible to assist the user indistinguishing between the relevant keys 408 and the non-relevant keys410.

FIGS. 5 and 6 present two other user interface presentations (500, 600,respectively). In these figures, the state of the user's currentinteraction with the application has changed because the user hasinvoked different application functions. For example, in the case ofFIG. 5, the user is currently browsing through a collection of VODassets. In FIG. 6, the user is currently attempting to browse through acollection of pictures. Different keys are deemed relevant andnon-relevant to these respective current states. For example, in thecase of FIG. 5, the navigation logic 212 determines that all of thenavigation keys 304 are relevant to the user's current interaction withthe application. Hence, the navigation logic 212 visually indicates thatall of the keys are relevant in the representation 406 by de-emphasizingnone of the keys. In FIG. 6, the navigation logic 212 determines thatjust the up arrow key, down arrow key and the OK key are relevant to theuser's current interaction with the application. Hence, the navigationlogic 212 visually indicates just these keys are relevant (by omittingor other otherwise de-emphasizing the left arrow key and the right arrowkey in the representation 406, which are collectively deemednon-relevant keys).

Through the above-described provisions, the user can be quickly andeffectively informed of the collection of keys on the RC device 112which can be activated to interact with the application. That is, therepresentation 406 guides the user's input activity so that it is moreclosely integrated with flow of the application itself, reducing theamount of “hunting” that the user must perform to find appropriate keyswhen interacting with the application in a particular application state.

FIG. 7 shows various ways in which the navigation logic 212 cansupplement the representation 406 to better alert the user to theidentity and location of relevant keys. According to one feature, thenavigation logic 212 animates one or more relevant keys. Animation cancomprise the presentation of a series of still images that simulatesmovement, an animated graphical presentation, a video substream, and soforth.

For example, in the user interface presentation 700, arrow 702 indicatesthat the navigation logic 212 animates the right arrow key (which is oneof the relevant keys at this current state), e.g., by making the rightarrow key move a slight jog to the right, and then back to its originalposition. In one case, the navigation logic 702 can produce thismovement when the user presses the right arrow key on the RC device 112.This helps confirm to the user that they have indeed pressed a key whichthe navigation logic 212 has assessed as being relevant. This at leastlets the user know that they are operating on the correct collection ofkeys on the RC device 112. In another case, the navigation logic 212 canproduce movement of the keys to invite the user to activate particularkeys (that is, prior to the user having activating these particularkeys).

In another implementation, instead of animating the relevant keysthemselves, the navigation logic 212 can provide other animated cueswhich point out the relevant keys, such as animated arrows or characterswhich point to the relevant keys. In another implementation, thenavigation logic 212 can also presentation animation when the useractivates a non-relevant key, such as by presenting a flashing “X”signal to indicate that the key that the user has pressed does not servea useful function in the current application state. Still otherpermutations of this design concept are possible.

Alternatively, or in addition, the navigation logic 212 can produceaudible cues which assist the user in identifying relevant keys on theRC device 112. Audio prompt 704 shown in FIG. 4 represents this concept.The audio prompts can be implemented by the navigation logic 212 as astored collection of messages, which can be correlated to differentapplication states using any kind of indexing strategy. As in the casewith animation, in one case, the audio prompts can alert the user to thefact that they have already pressed a certain key that is deemedrelevant. Or the audio prompts can encourage the user to activate acertain key before the user presses this key. Still other permutationsof this design concept are possible.

The representation 406 shown in FIGS. 4-7 only presents a small subsetof the keys of the RC device 112, namely just the application navigationkeys 304. In other scenarios, the navigation logic 212 can presents adifferent subset of keys, such as the media playback keys 302, and anyother combination of keys.

Alternatively, the user interface presentation 800 shown in FIG. 8illustrates the case where the navigation logic 212 presents arepresentation 802 of the entire RC device 112. The navigation logic 212can then highlight the keys that are relevant to the user's currentinteraction with an application, by removing non-relevant keys, or bydisplaying the non-relevant keys in a different manner than the relevantkeys. This implementation may better inform the user of the location ofrelevant keys, as it shows the relevant keys in the context of theentire RC device 112. The navigation logic can optionally includesupplemental cues, such as the animated arrow 804 or audio information(not shown), which further serve to point out the location of relevantkeys.

Lastly, FIG. 9 shows a case in which the navigation logic 212 actuallysends information back to the RC device 112 regarding the relevant keys.The control logic 222 of the RC device 112 can then apply thisinformation by generating visual and/or audio prompts on the RC device112 itself. FIG. 9 particularly shows the exemplary case in which thecontrol logic 22 causes relevant keys 902 to light up or glow on the RCdevice 112. This unambiguously identifies the keys which are relevant toa user's current interaction with an application. In this case, theplayback keys 302 have been deemed pertinent to the user's current statein interacting with the application. Other techniques can be used toprovide cues, such as by dynamically recessing non-relevant keys beneaththe face plate of the RC device 112, displaying telltale beeps or otheraudio prompts that lets the user know whether they have pressed arelevant key or a non-relevant key, and so forth.

C. Exemplary Method of Operation

FIG. 10 describes the operation of the navigation logic 212 in flowchartform. To facilitate discussion, certain operations are described asconstituting distinct steps performed in a certain order. Suchimplementations are exemplary and non-limiting. Certain steps describedherein can be grouped together and performed in a single operation, andcertain steps can be performed in an order that differs from the orderemployed in the example set forth in this disclosure. As many functionsdescribed in this flowchart have already been explained in priorsections, this section will serve primarily as a review of thosefunctions.

In step 1002 of procedure 1000, the navigation logic 212 determines acurrent state of a user's interaction with an application. In step 1004,the navigation logic 212 determines the RC device keys (or moregenerally, the input mechanisms) which are deemed relevant to thecurrent state. As described above, one way of performing this operationis to consult a rule set or lookup table, which maps current state intorelevant keys. In step 1006, the navigation logic 212 presents the userinterface presentation 114 which emphasizes the keys which have beendetermined to be relevant vis-à-vis the keys that have been determinedto be non-relevant. In step 1008, the navigation logic 212 determineswhether the state has changed, and if so, prompts the repetition of theabove-described steps so as to potentially highlight a differentcombination of relevant keys. In step 1010, the navigation logic 212determines whether the user has ceased interacting with the application,and if so, the procedure 1000 comes to an end.

Although the invention has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the invention defined in the appended claims is not necessarilylimited to the specific features or acts described. Rather, the specificfeatures and acts are disclosed as exemplary forms of implementing theclaimed invention.

1. A method for guiding a user in the use of a remote control (RC)device, wherein the RC device includes a plurality of input mechanisms,comprising: determining a current state of a user's interaction with anapplication, to provide a determined state; determining at least oneinput mechanism of the RC device that is relevant to the determinedstate, to provide at least one relevant input mechanism capable ofperforming an operational function specific to the determined state;displaying a representation of said at least one relevant inputmechanism on a user interface presentation of a presentation device,wherein the representation resembles a physical layout of said at leastone relevant input mechanism on the RC device, and wherein therepresentation de-emphasizes irrelevant input mechanisms of the RCdevice, distinguishing irrelevant input mechanisms from relevant inputmechanisms, wherein irrelevant input mechanisms are not capable ofperforming an operational function specific to the determined state, andwherein the displaying comprises: a media program or a display ofdigital pictures for user consumption, on a first part of the userinterface presentation, and the at least one relevant input mechanism ona second part of the user interface presentation.
 2. The method of claim1, wherein the application pertains to the presentation of mediaprograms to the user, and wherein the RC device is configured tonavigate among options associated with the presentation of the mediaprograms.
 3. The method of claim 1, wherein the determining of said atleast one relevant input mechanism comprises determining at least onerelevant key on the RC device that has a potential role in enteringinformation in the determined state.
 4. The method of claim 1, whereinthe displaying comprises showing a subset of the RC device's inputmechanisms on the user interface presentation.
 5. The method of claim 1,wherein the displaying comprises showing all of the RC device's inputmechanisms on the user interface presentation.
 6. The method of claim 1,wherein the de-emphasizing of the irrelevant input mechanisms comprisesomitting the presentation of the irrelevant input mechanisms.
 7. Themethod of claim 1, wherein the de-emphasizing of the irrelevant inputmechanisms comprises presenting the irrelevant input mechanisms in adifferent manner than said at least one relevant input mechanism.
 8. Themethod of claim 1, wherein the displaying further comprises animatingthe representation of said at least one relevant input mechanism to drawthe user's attention to said at least one relevant input mechanism. 9.The method of claim 1, wherein the displaying is further supplemented bythe presentation of audio information associated with saidrepresentation to draw the user's attention to said at least onerelevant input mechanism.
 10. The method of claim 1, wherein said atleast one relevant input mechanism comprises one or more applicationnavigation keys on the RC device.
 11. The method of claim 1, whereinsaid at least one relevant input mechanism comprises one or more keys onthe RC device for controlling the playback of a recorded media program.12. One or more computer readable storage media including machinereadable instructions for implementing the method of claim
 1. 13. Acomputer readable memory device storing navigation logic configured toguide a user in the use of a remote control (RC) device, wherein the RCdevice includes a plurality of input mechanisms, the navigation logiccomprising: logic configured to determine a current state of a user'sinteraction with an application, to provide a determined state; logicconfigured to determine at least one input mechanism that is relevant tothe determined state, to provide at least one relevant input mechanismcapable of performing an operational function specific to the determinedstate; logic configured to display a representation of said at least onerelevant input mechanism on a user interface presentation of apresentation device, wherein the representation resembles a physicallayout of said at least one relevant input mechanism on the RC device,wherein the representation de-emphasizes irrelevant input mechanisms ofthe RC device, distinguishing irrelevant input mechanisms from relevantinput mechanisms, wherein irrelevant input mechanisms are not capable ofperforming an operational function specific to the determined state, andwherein the displaying comprises: a media program or a display ofdigital pictures for user consumption, on a first part of the userinterface presentation, and the at least one relevant input mechanism ona second part of the user interface presentation.
 14. One or morecomputer readable storage media including machine readable instructionsfor implementing the navigation logic of claim
 13. 15. A system forpresenting media programs to a user, comprising: a presentation deviceconfigured to present the media programs; a processing device, coupledto the presentation device, configured to present the media programs onthe presentation device; a remote control (RC) device configured tointeract with the processing device, wherein the RC device includes aplurality of input mechanisms, wherein the processing device includesnavigation logic, and wherein the navigation logic comprises: logicconfigured to determine a current state of a user's interaction with theprocessing device, to provide a determined state; logic configured todetermine at least one input mechanism that is relevant to thedetermined state, to provide at least one relevant input mechanismcapable of performing an operational function specific to the determinedstate; logic configured to display a representation of said at least onerelevant input mechanism on a user interface presentation of thepresentation device, wherein the representation resembles a physicallayout of said at least one relevant input mechanism on the RC device,wherein the representation de-emphasizes irrelevant input mechanisms ofthe RC device, distinguishing irrelevant input mechanisms from relevantinput mechanisms, wherein irrelevant input mechanisms are not capable ofperforming an operational function specific to the determined state, andwherein the displaying comprises: a media program or a display ofdigital pictures for user consumption, on a first part of the userinterface presentation, and the at least one relevant input mechanism ona second part of the user interface presentation.
 16. The system ofclaim 15, wherein the logic for displaying is configured to show asubset of the RC device's input mechanisms on the user interfacepresentation.
 17. The system of claim 15, wherein the logic fordisplaying is configured to de-emphasize the irrelevant input mechanismsof the RC device by omitting the presentation of the irrelevant inputmechanisms.
 18. The system of claim 15, wherein the logic for displayingis configured to de-emphasize the irrelevant input mechanisms of the RCby presenting the irrelevant input mechanisms in a different manner thansaid at least one relevant input mechanism.